An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, I received a Pending Termination Notice for my Apple Developer Program account. I submitted my first appeal on May 19, 2026. After receiving no response for an extended period, I submitted a second appeal with additional clarification and information. Most recently, I opened an Apple Developer Program Support case on June 2, 2026. I received the automatic confirmation email and case ID, but I have not received any further communication. At this time: My App Store Connect account remains accessible. I have not received a final decision. I have not received any request for additional information. I have not received any update regarding the status of the review. I understand that account reviews may take time, but I am unsure whether this length of silence is normal for a Pending Termination Notice case. Has anyone experienced a similar situation? Is there any recommended way to follow up, or should I simply continue waiting for a response from Apple? Thank you for any guidance.

Hello, Our iOS app’s TestFlight external testing build has been stuck in “Waiting for Review” for several days. This is for TestFlight External Testing, not an App Store public release submission. We have already provided the Beta App Review Information, including review notes, test instructions, contact information, and a working demo account. Current situation: App name: Linic Platform: iOS Submission type: TestFlight External Testing Status: Waiting for Review Submitted date: June 4 ~ June 5, 2026 Build number: 1.4.2(8)、1.4.3(9) Bundle ID: com.lincept.linny Beta App Review Information: already updated Demo account: provided in App Store Connect We would like to understand whether this is currently expected queue behavior, whether TestFlight external beta reviews are experiencing delays, or whether there is any additional information we should provide to help the review proceed. Has anyone recently experienced a similar delay with TestFlight External Testing builds stuck in “Waiting for Review”? If so, did contacting Apple Developer Support or submitting an expedited review request help? Thank you.

Hello, Our iOS app’s TestFlight external testing build has been stuck in “Waiting for Review” for several days. This is for TestFlight External Testing, not an App Store public release submission. We have already provided the Beta App Review Information, including review notes, test instructions, contact information, and a working demo account. Current situation: App name: Linic Platform: iOS Submission type: TestFlight External Testing Status: Waiting for Review Submitted date: June 4 ~ June 5, 2026 Build number: 1.4.2(8)、1.4.3(9) Bundle ID: com.lincept.linny Beta App Review Information: already updated Demo account: provided in App Store Connect We would like to understand whether this is currently expected queue behavior, whether TestFlight external beta reviews are experiencing delays, or whether there is any additional information we should provide to help the review proceed. Has anyone recently experienced a similar delay with TestFlight External Testing builds stuck in “Waiting for Review”? If so, did contacting Apple Developer Support or submitting an expedited review request help? Thank you.

I'm hoping someone here has been through a similar situation and can help. Our app was rejected under Guideline 4.3 (Design Spam), but I believe this is a misunderstanding. This app was previously approved under a different developer account — we had to resubmit under a new account due to an internal business restructuring. The app itself has not changed at all. Here's the timeline: May 24 — Filed an appeal May 26 — Filed another appeal Jun 4 — Filed another appeal Jun 7 (today) — Filed yet another appeal It has now been over 2 weeks since the first appeal with no response whatsoever. This is genuinely just a resubmission of an already-approved app due to a company account change — not an attempt to game the review process in any way. The situation is urgent as we have a launch scheduled for this week. Every day of delay is directly affecting our users and timeline. Has anyone experienced this? How did you get it resolved? Is there any way to escalate beyond the Resolution Center? Any advice would be truly appreciated.

I have submitted my app since the last 3 weeks, until now it is still "Waiting for review" I also did not receive any errors or notifications saying why its stuck. Can someone help me?

Hello, I need help with an App Store Connect review issue that has become very frustrating. My iOS app “Mamos Trend Color” has been stuck in “Waiting for Review” since April 23, 2026 at 09:41. App details: App name: Mamos Trend Color App Apple ID: 6762326235 Platform: iOS Version: 1.1 Current status: Waiting for Review Submitted on: April 23, 2026 at 09:41 I already contacted Apple Developer Support. On May 26, 2026, Developer Support confirmed that there was no update on the review and said the issue had been escalated to the App Review team. Unfortunately, nothing has changed since then. The app is still not in review, there is no rejection, no message, no request for information, and no visible progress in App Store Connect. This is not a normal review delay anymore. It looks like the submission is stuck somewhere in the system. I am honestly very disappointed by the lack of transparency. I paid for the Apple Developer Program, submitted the app correctly, followed the App Store Connect process, opened a support request, waited after escalation, and I still have no clear answer. I fully understand that the Apple Developer Program fee does not guarantee app approval. But I do expect a working review process, clear communication, and a way to resolve a submission that appears blocked for weeks. Can someone from Apple please manually check this submission or tell me exactly what I need to do? Specifically: Is the app still waiting in the normal review queue? Has the review actually been escalated to App Review? Is there a hidden issue with the app record? Should I remove the current submission and submit a new build? Is there another official channel to resolve this kind of stuck status? I can provide the Developer Support case number privately if needed. Thank you.

Hello, I am posting here because I no longer have access to the communication channels that were previously available to discuss my developer account with Apple. My appeal was denied, but Apple informed me that I could submit a reinstatement request after addressing the concerns that had been identified. Following that communication, I spent considerable time reviewing my applications, metadata, screenshots, codebase, user flows, and business practices. Although I do not believe my account was involved in dishonest or fraudulent activity, I nevertheless made extensive changes in an effort to address any potential concerns Apple may have had. The main difficulty is that the specific conduct that led to the termination decision was never clearly explained to me. Apple cited Section 3.2(f) and provided examples of prohibited behavior, but did not identify which specific action or activity was associated with my account. As a result, I was left attempting to correct every possible issue without understanding what the actual concern was. In addition, throughout my participation in the Apple Developer Program, I had never previously encountered a notice, suspension, or similar action of this nature. This made it even more difficult for me to understand what specific issue Apple believed had occurred and how best to address it. While I was still implementing changes and preparing what I believed would be a reinstatement submission, I received a termination notice. Since the termination, I have lost access to the Contact Us page and the communication channels that were previously available to me. I would therefore appreciate guidance from Apple or from developers who may have experienced a similar situation: How is a developer expected to submit a reinstatement request after termination if the Contact Us page is no longer accessible? Is there an alternative channel through which reinstatement requests can be submitted? Has anyone successfully submitted a reinstatement request after account termination and received a review? I am not asking Apple to reverse its decision through this forum. I am simply trying to understand how a developer is expected to submit a reinstatement request after termination when the previously available communication channels are no longer accessible. Thank you for your time.

Hi everyone, I’m having an issue with an app update in App Store Connect and wanted to ask if there is anyway to get urgent support. The update was approved successfully, and the status has been showing as “Ready for Distribution” for over 4 days. Usually, once an update reaches this stage, it becomes available on the App Store within a few hours, but this time it still hasn’t appeared. So far, I’ve checked the following: The app review was completed successfully. The version is approved and showing a green status. I contacted Apple Developer Support a few days ago. Case ID: 102906011756 I have not received any update from Apple Support yet, other than the initial confirmation. Has anyone else recently had an approved app update stay in “Ready for Distribution” for several days? Is there anything I can do from App Store Connect to push the release forward, or do I just need to wait for Apple Support? Any suggestions would be appreciated. Thanks.

To the Apple Review and Developer Support Teams, We are experiencing the same issue described in this thread: https://developer.apple.com/forums/thread/827016 Our application has been rejected under Guideline 2.1 - Performance because the subscription plans do not load during the App Review process. According to the review feedback, there's an error indicating that the In-App Purchases product list is empty. We are unable to reproduce this issue on our side. The subscription screen works correctly in TestFlight on multiple physical devices and with sandbox tester accounts. The paywall loads successfully, localized prices are returned correctly, and test purchases can be completed without errors. We have verified the following: All subscription products are attached to the submitted app version in App Store Connect. The product identifiers used in the application match the identifiers configured in App Store Connect. The relevant agreements, tax information, and banking details are active and up to date. The same build works correctly in TestFlight. The issue appears to occur exclusively in the App Review environment. This makes it difficult for us to diagnose the root cause or validate a fix. Could you please investigate whether there is an issue affecting StoreKit product retrieval during the review process? Any logs, diagnostics, or guidance on how to reproduce the App Review environment behavior would be helpful. Submission details: Date Submitted: Jun 1, 2026 at 2:01 PM Submission ID: 1260550e-ba11-4cbe-925a-7694f89ce715 Thank you for your assistance.

I submitted an updated version of my app for review on May 18, 2026, and its status has remained "Waiting for Review" ever since. It has now been more than two weeks without any progress or communication from Apple. To resolve the issue, I have: Submitted multiple support tickets through Apple Developer Support. Received the standard message that I would receive a response within 48 hours. Waited more than 15 days, but have not received any reply to any of my tickets. Attempted to contact Developer Support by phone during U.S. business hours, but after waiting on hold for more than two hours, I was unable to reach anyone. This delay is affecting my ability to release important updates to my users, and I am running out of options. Has anyone experienced a similar situation recently? Is there any other channel or escalation process that I can use to get assistance or have my submission reviewed? Any guidance would be greatly appreciated. Thank you.

Hello everyone, I submitted the first update for my app on April 14. On April 18, I canceled that submission and immediately resubmitted it the same day, as many people suggested that resubmitting might help speed up the review process. Today is June 4, and after 47 days, the update is still stuck in “Waiting for Review.” I’ve seen that many other developers are experiencing the same issue, but 47 days is a very long time for me, and I have no idea how much longer I should expect to wait. I hope we can all find a solution to this situation soon. Any advice, insights, or shared experiences would be greatly appreciated. Thank you all.

Hi everyone, I’m based in Europe, and I’m trying to fully understand the current App Store payment rules for an iOS app that sells digital services or premium functionality used inside the app. My goal is not to bypass App Store rules, but to implement the correct, compliant payment flow depending on the user’s region and the App Store requirements that apply there. The app would offer things like premium features, credits, or access to digital functionality inside the iOS app. The payment flow I would ideally like to support, where allowed, is: iOS app -> Cloud ahndling -> Stripe Checkout page -> user pays -> Stripe handling -> my backend marks the user as premium What I’m trying to understand is whether this flow is allowed, restricted, or prohibited depending on the user’s App Store storefront / region. My questions are: For digital goods, subscriptions, credits, or premium features used inside an iOS app, is Apple In-App Purchase still required by default? In which regions, exactly, can an iOS app use or link to an external payment provider such as Stripe for digital services used inside the app? For users in the United States, after the Epic Games v. Apple changes, can an app show an external payment option such as “Subscribe on the web” or “Pay with Stripe”? If yes, what are the exact requirements, limitations, wording rules, Apple fees, or reporting obligations? For users in the European Union, under the DMA-related rules, does Apple allow external purchases through Stripe or a web checkout? If yes, do I need specific Apple entitlements, StoreKit External Purchase APIs, Apple approval, transaction reporting, or payment of Apple fees? For the rest of the world, should I assume that Apple IAP is mandatory for digital content, subscriptions, credits, and premium app functionality unless Apple has a specific regional program allowing external payments? What is the correct way to determine which payment flow a user should see? Should this be based on the user’s App Store storefront / StoreKit storefront, rather than IP address, device locale, billing address, or country selected manually by the user? Would a regional routing approach like this be compliant? if App Store storefront == US: show Apple-compliant external purchase link / Stripe option if allowed elif App Store storefront is in the EU and the app has the required Apple entitlement: show Apple-compliant external purchase flow else: show Apple In-App Purchase only If a user pays through Stripe or another external checkout in a region where external payments are allowed, can my backend unlock premium features inside the iOS app? Or are there restrictions on granting access inside the app when the purchase was not completed through Apple IAP? For a first App Store release, is the safest approach to launch with Apple IAP only, then later add external payment options only in regions where Apple explicitly allows them? For developers who have recently submitted apps with external payment links for digital services: Which countries or storefronts were accepted? Did App Review require special entitlements? Were there specific wording or UI requirements? Did Apple require transaction reporting or apply additional fees? Were there differences between the US, EU, and other regions? In short, I’m trying to understand the practical compliant architecture: iOS app = Apple IAP by default external Stripe / web checkout = only where regionally allowed by Apple backend = unlock premium access after valid payment, whether Apple IAP or approved external payment payment UI = adapted based on App Store storefront / region I would really appreciate answers from developers, App Review experiences, or anyone familiar with the current Apple rules after the Epic ruling, DMA changes, and Apple’s External Purchase Link / StoreKit External Purchase programs. Thanks!

After a 2.3.2 rejection (two promoted subscriptions had identical display name + description), I withdrew the review submission to edit the subscription metadata. The app version moved to "Developer Rejected," but both auto-renewable subscriptions stayed stuck in "In Review." There is no active review submission attached to them anymore, yet: The subscription metadata (display name / description) is locked / not editable. There is no "Remove from Review" control on the subscription page or the version page. The version page no longer shows an "In-App Purchases and Subscriptions" section. Has anyone hit this orphaned "In Review" state? Is there a developer-side way to release a subscription from review, or is contacting Developer Support the only path? Appreciate any pointers, I'm on a deadline. App: Mossly: Plant Care Journal - Apple ID 6770594348 Subscription Group: Mossly Premium - 22098178 Subscriptions, both stuck: Mossly Premium - Monthly - 6770598241 (com.mossly.app.monthly) Mossly Premium - Yearly - 6770599597 (com.mossly.app.annual1)

Hello Apple Staff, I am writing again because my app review issue is still unresolved, and I am becoming increasingly concerned that the submission may not be properly moving through the normal App Review queue. App ID: 6760743106 Submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 Current status: Waiting for Review At first, I waited for approximately two days with no progress. Since the status did not move at all, I submitted a new build and resubmitted the app, thinking there may have been an issue with the previous submission. However, it has now been nearly one week since the resubmission, and the app is still stuck in Waiting for Review. The status has not moved to In Review. I have already tried multiple official support channels: I contacted Apple Developer Support by phone. I submitted an email support request. I posted on the Developer Forums. I submitted an expedited review request. Unfortunately, nothing has changed so far, and I have not received any clear confirmation that the current submission is properly queued for review. I fully understand that App Review times can vary, and I sincerely respect the work of the App Review team. However, this situation is becoming very serious for us. The update is important for our users, and the continued delay is creating significant operational and business impact. At this point, I am not asking to cancel the submission or resubmit the app again. I am asking whether Apple can please verify the following: Whether the current submission is properly queued for App Review. Whether there is any internal processing or queueing issue preventing the review from starting. Whether there is any action required from my side that is not visible in App Store Connect. If possible, could an Apple Staff member please escalate this case to the App Review team or confirm that the submission is correctly queued? I would be extremely grateful for any help or clarification. We are feeling very stuck because we have tried every support channel available to us, but the app remains in Waiting for Review with no progress. Thank you very much for your time and support.

Hello fellow developers and Apple Review Team, I am reaching out to the community and any Apple App Review representatives here as a matter of absolute business urgency. Our essential health app, BeatO Diabetes Management (App ID: 1070739458), has been effectively paralyzed in the review queue for nearly 40 days (since late April 2026), severely impacting thousands of chronic care patients who rely on our ecosystem daily for blood glucose tracking. We are completely aligned with Apple’s rigorous safety standards, but we have reached an operational dead end where detailed, compliant answers are met with week-long silence. ⏱️ The Timeline of the Review Deadlock: Late April 2026: Initial build submitted. Flagged under Guideline 1.4.1 (Safety - Physical Harm) regarding our connection to external hardware (a CE-certified glucometer). May 12, 2026: We provided absolute regulatory documentation: official CE certifications, supplier details, clinical validation reports, and proof of prominent American Diabetes Association (ADA) threshold disclaimers inside the UI. May 15, 2026: Apple responded stating: "Your submission's review will require additional time... We do not require any further information at this time." May 26/27, 2026: After a prolonged freeze, we halted the initial release to clear the pipe and submitted a completely fresh build (Submission ID: a0bf3856-693b-4577-adc7-9199a5f9fe34) hoping to reset any stuck internal states. May 27, 2026: Apple requested information under Guideline 2.1 (Information Needed) asking two specific questions about algorithmic personalization and our "tailored diabetes program" marketing text. May 27, 2026: Within a couple of hours, we provided an exhaustive, definitive response: Clarified ADA Guidelines: Confirmed that high/low glucose classifications are strictly based on standard published clinical data (ADA Standards of Care) and explicitly disclosed in our Terms & Conditions, not personalized by an algorithm. Clarified Program Architecture: Proved that 0% of the program is generated by an algorithm. The app acts purely as an introductory storefront/brochure. The actual care management is fulfilled entirely offline directly by human doctors and certified medical professionals. It is definitively not an algorithmic medical device feature. May 28, 2026 to Present: The app was re-entered into the "In Review" state and has sat completely frozen ever since. 🛑 The Core Problem & Business Impact We have successfully provided every piece of documentation Apple has asked for - legal, medical, clinical, and architecture definitions. The reviewer explicitly stated they have everything they need, yet we are trapped in an endless manual review loop. Because our app manages active diabetic health metrics, this prolonged delay prevents us from deploying critical performance optimizations and bug fixes. Our patient support lines are flooding, and our operational product roadmap for the quarter is completely stalled. 🙏 Request to the Community / Apple Engineers Has anyone else dealing with health hardware/software integration hit this specific wall where your answers are fully compliant, but the review desk simply stops processing the ticket? If any Apple App Review moderators or App Store Connect engineers see this, we respectfully request an internal escalation or an App Review Appointment to unblock this build. We are ready to jump on a call immediately to provide any final clarity required. App Name: BeatO Diabetes Management App ID: 1070739458 Latest Submission ID: a0bf3856-693b-4577-adc7-9199a5f9fe34 Thank you for your time and guidance. Regards, Sanketkumar Biswas

hello app review: My app was submitted for review at 11:07 PM on June 1st, and as of now, on the afternoon of June 4th, it has not yet entered the review process. Please urge the review team to proceed with the review as soon as possible. If there are any areas that need to be rectified, we will immediately make the necessary changes. Thank you

I have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. Thank you.

Hello! My subscriptions have been stuck in review for a while. I have been chasing my tail trying to get the sandbox purchases to work but the subscriptions are not returning after "sale". Is this because the subscriptions are still in review? Will the purchase ever return a product in the sandbox environment if the products are still in review? How do we get the subscriptions approved? I have submitted them with the app multiple times. The app is rejected because I can't complete it without the subscriptions but the subscriptions are never reviewed. Help!